Network system capable of grouping multiple service requests

ABSTRACT

A network system managing a network service can receive queries and service requests from multiple user devices. The network system can manage the network service such that multiple service requests can be fulfilled by a single service provider. In addition, the network system can dynamically compute parameters associated with the network service. The computation of the parameters can be based on pending service requests or anticipated demand for the network service.

BACKGROUND

A conventional network service may allow a requesting user to requestservice associated with a selection of one or more items from an entityto be fulfilled by a service provider. However, each service providertypically can only fulfill a single service request at a time. Inaddition, in such conventional network services, parameters such asdelivery fees associated with the network service are typically fixed toa default value.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure herein is illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings in which likereference numerals refer to similar elements, and in which:

FIG. 1 is a block diagram illustrating an example network system incommunication with user devices, service provider devices, and entities,as described herein;

FIG. 2 is a flow chart describing an example method of operating anexemplary network system, according to examples described herein;

FIGS. 3A-3D are figures illustrating exemplary user interfaces for auser application for a network service, as described herein;

FIG. 4 is a block diagram that illustrates a computer system upon whichexamples described herein may be implemented; and

FIG. 5 is a block diagram illustrating an example user device executingand operating a designated user application for communicating with anetwork service, according to examples described herein; and

FIG. 6 is a block diagram illustrating an example service providerdevice executing and operating a designated service provider applicationfor communicating with a network service, according to examplesdescribed herein.

DETAILED DESCRIPTION

A network service, which is implemented by a computer system(s)(referred to herein as a “network system” for purposes of simplicity),is provided herein that links service providers (e.g., drivers,couriers, autonomous vehicles (AVs), etc.) with requesting usersthroughout a given geographic region (e.g., a metroplex such as the SanFrancisco Bay Area). In doing so, the network service communicates witha pool of service providers over the given geographic region, eachoperating one or more computing devices (“service provider devices” or“provider devices”). The network system receives requests for services(e.g., a delivery service, a courier service, etc.) from requestingusers via a designated user or client application (“user application”)executing on the users' mobile computing devices (“user devices”).

Furthermore, the network system enables users to select, via the userapplication, items provided by entities. As referred to herein, anentity can correspond to an individual, a company, a group, a vendor ormerchant, etc., that provides one or more goods or items for sale (e.g.,a chef, a baker, a restaurant, a café, a store, etc.). A service requestreceived by the network system can include a requesting user's selectionof items provided by an entity to be transported by the service providerto a service location for delivery to the requesting user. In thecontext of a delivery service (e.g., food ordering and deliveryservice), the service location can be a delivery location at which theservice provider is to deliver the requested items to the requestinguser. In response to the service request, the network system can notifythe entity of the user's selection. In addition, the network system canidentify an available service provider to fulfill the user's request.The network system can transmit an invitation to a provider device ofthe identified service provider, who can accept the invitation tofulfill the requested service.

In various aspects, before a user is enabled to make a selection on theuser application to submit a service request, the user's user device cantransmit a query to the network system. The query can be transmitted inresponse to the user launching or activating the user application. Thequery can also be submitted in response to the user's selection of auser interface feature (e.g., a soft selection feature for “Search” or“Submit”). In addition, the query can be automatically or periodicallytransmitted by the user application or a component of an operatingsystem of the user device. In various aspects, a query can include adesired service location determined using location data generated by theuser device or inputted by the requesting user via the user application.The service location can be a location to which the service provider isto deliver items to the requesting user. The query can also include adesired service time (e.g., a time for which the requested service is tobe completed or fulfilled by the service provider). In response toreceiving the query, the network system can identify entities (e.g.,nearby entities, entities located within a specified or predetermineddistance from the service location, entities located in a particulargeographic region, etc.) that offer items available for selection by theuser. In some examples, the network system can also determine availableitems offered by the identified entities that satisfy the criteriaimposed by user inputs (e.g., user preferences for items, service time,etc.). The network system can transmit content data to the user deviceto enable or cause the user device to display, within the userapplication, the identified entities and/or the available items. Basedon a user selection within the user application, the user device cantransmit, to the network system, a service request. The service requestcan include data indicating the user's selection of one or more of theavailable items. In response to receiving the service request, thenetwork system can notify the relevant entity(ies) of the user'sselection and invite a service provider(s) to fulfill the user's servicerequest (e.g., by delivering the user's selected items from the relevantentity(s) to the user at the desired service location). The networksystem can also determine a route for the service provider(s). The routecan include route segments to the relevant entity(ies) and to theservice location.

Embodiments described herein allow for the network system to manageservice providers, service requests, and the network service such that asingle service provider can service multiple service requests submittedby different users. The network system can determine whether to groupservice requests by their associated entities. For instance, the networksystem can determine that two or more service requests for items fromthe same entity or from entities located within a certain distance canbe serviced by a single service provider. Similarly, the network systemcan determine to group service requests by their service locations.

As described herein, a parameter (e.g., booking fee, service charge,delivery fee, etc.) can be associated with a service request. Theparameter can have a predetermined or default value (e.g., flat-ratedelivery or service fee) or can be dynamically determined based onfactors such as travel distance for the service provider, time ofservice, etc. Embodiments described herein allow for the network systemto dynamically compute one or more parameter values in response to aquery from a user based on pending service requests from other usersand/or based on anticipated demand for the network service. If the usermakes a selection within the user application to submit a servicerequest following the query, one of the one or more dynamically computedparameter values can be associated with the service request.

According to embodiments, each of the one or more parameter values canbe determined specifically for a corresponding entity. For example, auser device can transmit, to the network system, query datacorresponding to a query for service. The query data can indicate aservice location associated with the query for service. In response, thenetwork system can dynamically determine a plurality of parameters, eachof the parameters being associated with an entity. In some situations,only a subset of the plurality of parameters are dynamically determined;one or more of the plurality of parameters corresponding to a subset ofthe entities can have a predetermined or default value.

In some implementations, the network system can dynamically determinevalues for parameters based on pending service requests received fromother users. As used herein, a pending service request can refer to aservice request received by the network system for which the requestedservices are pending to be fulfilled. For example, in response to aquery from a user, the network system can determine that there is atleast one pending service request from another user for items from aparticular entity to the service location associated with the query.Based on this determination, the network system can dynamicallydetermine the parameter associated with the particular entity inresponse to the query. The dynamically determined value for theparameter can be lower than the predetermined or default value becausethe network system can leverage existing resources (e.g., a serviceprovider fulfilling the at least one pending service request) to servicea request from the user for items from the particular entity. Inaddition or as an alternative, the network system can dynamicallydetermine parameter values based on anticipated demand. The networksystem can dynamically determine parameter values based on historicaldata associated with the network service. Based on the historical data,the network system can determine a metric representative of anticipateddemand associated with the particular entity, the service location, andthe service time. The metric can also be determined based on third partydata, including data regarding weather, scheduled events (e.g., asporting event), that may affect demand associated with the networkservice.

In various aspects, the network system can further determine, for eachdynamically determined parameter, a corresponding time interval. Thetime interval can be a window of time for which the dynamicallydetermined parameter is to be valid. For a parameter determined based onpending service requests, the associated time interval can be based onexpected time of fulfillment for the pending service requests. For aparameter determined based on anticipated demand for the networkservice, the associated time interval can be based on historical dataassociated with the network service indicating times of peak or elevateddemand for the network service. Upon the expiration of an associatedtime interval, the parameter can be recomputed or can be assigned thedefault parameter value.

In some examples, the network system can cause the user application todisplay a notification of a dynamically-computed parameter to the userwithout the need for user action or input. As one example, the userapplication can periodically transmit a query to the network systemwhile it is being executed in the background on the user device. Theuser application can also automatically transmit a query to the networkdevice in response to detecting that location data generated by the userdevice indicates that the user has changed his or her location. Thequery can alternatively be transmitted by the operating system of theuser device or a component thereof. In response to receiving the query,the network system can dynamically determine one or more parameters(e.g., based on pending service requests or based on anticipated demand)associated with entities for service to a location indicated in thequery (e.g., using location data generated by the user device). Thenetwork system can cause the user device to display the one or moreparameters via, for example, a push notification. For example, the userdevice can receive a push notification to inform the user that adynamically determined parameter associated with a particular entity forservice to a service location near the user's current location is belowa default or threshold value (e.g., a dynamically determined booking feeis below a default, flat price). As another example, the network systemcan dynamically determine one or more parameters for notification to theuser without receiving a query from the user device. Rather, the networksystem can determine one or more parameters for a service location savedin the user's profile (e.g., a favorite location, home address, workaddress). The network system can thus transmit push notifications to theuser device to notify the user of one or more reduced parameters forlocations relevant to the user. The notifications can be furthercustomized such that time intervals can be associated with the servicelocations saved in the user's profile. For instance, the network systemcan cause notifications regarding reduced parameters to be displayed onthe user device for the user's work address between the specific hoursof 12:00 PM to 1:00 PM Mondays through Fridays. In this manner, the usercan receive useful and relevant notifications without the need for theuser device to repeatedly or constantly transmit queries to the networksystem to indicate a current location of the user. In each of theseexamples, the user can further opt to receive notifications for only theentities in which the user is interested (e.g., favorite or preferredvendors).

In various aspects, the network system can generate content data inresponse to queries and transmit content data to the user devices. Thecontent data can cause the user devices to display a variety ofinformation the user may need to make one or more selections as toentities and items for service. For instance, the user devices canutilize the received content data to display menu items for selection bythe user. In addition, information such as reviews of specific entitiesor available items by other users of the network service can bedisplayed. The content data can further cause the user devices todisplay the parameters associated with each of the entities. Inaddition, the content data can cause the user devices to display text orgraphics to indicate that a parameter associated with a particularentity is dynamically computed or different compared to the defaultvalue. For instance, the user device can display a downward arrow nextto the parameter to indicate that the parameter is lower than thedefault value. The content data can also cause the user device todisplay a time interval associated with a dynamically determinedparameter.

In some examples, the content data can include data to displayrecommendations regarding particular entities based on parametersassociated with the particular entities. For instance, in response todynamically determining a parameter that is lower than the defaultvalue, the network system can generate content data that includes datacorresponding to a recommendation to the user regarding the particularentity. The recommendation can be displayed on a home screen of the userapplication notifying the user that the parameter associated with theparticular entity is lower than the default value for an interval oftime. The displayed recommendation can also include recommendationsregarding particular items in which that the user may be interested(e.g., based on the user's past service requests, based on user profileinformation, based on user preferences, etc.). The recommendation can bea promotion that indicates that a dynamically determined parameter isvalid for a certain amount of time. The user device can further renderuser interface features for the user to claim the promotion and tosubmit a service request based on the promotion.

According to embodiments, the network system can select a serviceprovider from a pool of service providers in the geographic region tofulfill multiple service requests from requesting users. The networksystem can communicate with provider devices operated by serviceproviders to receive data including data regarding location (e.g.,geo-location data generated by the provider device) and status (e.g.,indicating whether a service provider is available to fulfill a servicerequest). The network system can select the service provider based onlocation and status. For example, the network system can select aservice provider that is located proximately (e.g., within a mile) tothe entities and/or to the service location associated with the servicerequests. The network system can also select a service provider based ona provider type associated with the service provider (e.g., automobile,motorcycle, bicycle, on-foot, etc.). For instance, the network systemcan select a service provider based on the service provider's providertype that is determined to particularly suit the service location,entity locations, and/or a route (or a portion thereof) determined bythe network system (e.g., route to the entity locations and to theservice location). For instance, if the service location, entitylocations, and/or the route are located in a particularly dense urbanenvironment, the network system can determine to select a serviceprovider having a bicycle provider type. On the other hand, if the routeincludes a segment over a highway or an expressway, the network systemcan select a service provider having an automobile provider type. Thenetwork system can transmit, to the selected service provider, aninvitation to fulfill the requested service. In addition, the networksystem can select a service provider based on service capacity. Forinstance, in a delivery service context, the service capacity can be acargo capacity for items selected by requesting users. As an example,the network system can determine a service capacity requirement based onthe particular items selected in service requests that are grouped to beserviced by a single service provider. The network system can maintainor access records corresponding to a service capacity requirements forall items provided by entities. Based on the determined service capacityrequirement for the grouped service requests, the network system canselect an appropriate service provider from the pool of serviceproviders. For instance, for a group of service requests having a largenumber of selected items, the network system can select and transmit aninvitation to a service provider operating a large capacity vehicle.

According to embodiments, in response to receiving a service request,the network system can process the request data, identify items selectedby the requesting user, and transmit data regarding the selected itemsto corresponding entity(ies). Such information can allow the entities tobegin preparing the one or more selected items. In addition, the networksystem can transmit additional information to the entity(ies) regardingthe selected items while the service request is pending (e.g., in queueto be prepared by the entity(ies)). For example, the network system caninform the entity(ies) to delay or expedite the preparation of the itemssuch that the service request can be serviced by a particular serviceprovider (e.g., a service provider servicing another service request).In addition, the network system can, based on historical data relatingto demand of specific items at particular times, transmit data to theentities to allow them to prepare items of high demand. In this manner,the entities can be proactively informed to prepare high-demand itemsfor service before service requests for those items are received by thenetwork system. As another example, the network system can determine,based on historical data, that there is a high likelihood that thehigh-demand items will be requested by one or more users for service ata particular location. In response to this determination, the entitiescan proactively prepare these items and the network system can notifythe service provider fulfilling a pending service request to pick upthese high-demand items for delivery to the service location inanticipation of expected service requests for these items.

In certain implementations, the network system can determine a route fora service provider to take in fulfilling service requests received bythe network system. The route can include route segment(s) to theentity(ies) associated with the service requests and route segment(s) tothe service location(s) associated with the service requests. If theroute includes route segments to multiple entities or multiple servicelocations, the network system can determine an optimal sequence ofentities and/or service locations. The optimal sequence can bedetermined based on estimated preparation times of items associated withthe service requests, service request status data received from theentities, traffic conditions, and the like. For instance, a first entitycan be sequenced before a second entity based on the network system'sdetermination that item(s) being prepared by the first entity will becompleted before item(s) being prepared by the second entity. Inaddition, the route for the service provider can including timinginformation (e.g., time to depart) such that the service providerarrives at an entity at or around the time when the entity is estimatedto have finished preparing item(s). The network system can also optimizethe route based on travel time and/or travel distance. In this manner,the network system can minimize wait times by the service provider(e.g., waiting for items to be prepared at the respective entities'locations) and by the requesting user. In various aspects, the networksystem can also determine the optimal route based on traffic information(e.g., historical traffic patterns, real-time traffic data, predictedtraffic patterns, etc.).

Among other benefits, the examples described herein achieve a technicaleffect of improving the network system's management of resources. In oneaspect, by leveraging pending service requests in fulfilling servicerequests, the network system can reduce bottlenecks in providingservices and improve throughput. In particular, by grouping multipleservice requests such that they can be fulfilled by a single serviceprovider, embodiments described herein improve the network system byimproving the service capacity of the network service, particularlyduring peak-demand hours. In addition, by dynamically determiningparameters such as delivery or service fees based on pending servicerequests or anticipated demand, embodiments described herein allow formore efficient management of service providers by encouraging requestingusers to submit service requests to “bandwagon” with other pending oranticipated service requests. In this manner, a single service providercan fulfill a plurality of service requests, thereby increasing theefficiency of the network system.

As used herein, a computing device refers to devices corresponding todesktop computers, cellular devices or smartphones, personal digitalassistants (PDAs), laptop computers, virtual reality (VR) or augmentedreality (AR) headsets, tablet devices, television (IP Television), etc.,that can provide network connectivity and processing resources forcommunicating with the system over a network. A computing device canalso correspond to custom hardware, in-vehicle devices, or on-boardcomputers, etc. The computing device can also operate a designatedapplication configured to communicate with the network service.

One or more examples described herein provide that methods, techniques,and actions performed by a computing device are performedprogrammatically, or as a computer-implemented method. Programmatically,as used herein, means through the use of code or computer-executableinstructions. These instructions can be stored in one or more memoryresources of the computing device. A programmatically performed step mayor may not be automatic.

One or more examples described herein can be implemented usingprogrammatic modules, engines, or components. A programmatic module,engine, or component can include a program, a sub-routine, a portion ofa program, or a software component or a hardware component capable ofperforming one or more stated tasks or functions. As used herein, amodule or component can exist on a hardware component independently ofother modules or components. Alternatively, a module or component can bea shared element or process of other modules, programs or machines.

Some examples described herein can generally require the use ofcomputing devices, including processing and memory resources. Forexample, one or more examples described herein may be implemented, inwhole or in part, on computing devices such as servers, desktopcomputers, cellular or smartphones, personal digital assistants (e.g.,PDAs), laptop computers, VR or AR devices, printers, digital pictureframes, network equipment (e.g., routers) and tablet devices. Memory,processing, and network resources may all be used in connection with theestablishment, use, or performance of any example described herein(including with the performance of any method or with the implementationof any system).

Furthermore, one or more examples described herein may be implementedthrough the use of instructions that are executable by one or moreprocessors. These instructions may be carried on a computer-readablemedium. Machines shown or described with figures below provide examplesof processing resources and computer-readable mediums on whichinstructions for implementing examples disclosed herein can be carriedand/or executed. In particular, the numerous machines shown withexamples of the invention include processors and various forms of memoryfor holding data and instructions. Examples of computer-readable mediumsinclude permanent memory storage devices, such as hard drives onpersonal computers or servers. Other examples of computer storagemediums include portable storage units, such as CD or DVD units, flashmemory (such as carried on smartphones, multifunctional devices ortablets), and magnetic memory. Computers, terminals, network enableddevices (e.g., mobile devices, such as cell phones) are all examples ofmachines and devices that utilize processors, memory, and instructionsstored on computer-readable mediums. Additionally, examples may beimplemented in the form of computer-programs, or a computer usablecarrier medium capable of carrying such a program.

Some examples are referenced herein in context of an autonomous vehicle(AV) or self-driving vehicle (SDV). An AV or SDV refers to any vehiclewhich is operated in a state of automation with respect to steering andpropulsion. Different levels of autonomy may exist with respect to AVs.For example, some vehicles may enable automation in limited scenarios,such as on highways, provided that drivers are present in the vehicle.More advanced AVs can drive without any human assistance from within orexternal to the vehicle. Such vehicles are often required to makeadvanced determinations regarding how the vehicle behaves givenchallenging surroundings of the vehicle environment.

System Descriptions

FIG. 1 is a block diagram illustrating an example network system incommunication with user devices, service provider devices, and entities.Network system 100 can manage a network service within a givengeographic region (e.g., (e.g., a metroplex such as the San FranciscoBay Area). The network system 100 communicates with provider devices 190operated by service providers 192 and with user devices 195 operated byusers 197. Using the network service provided by the network system 100,users 197 can view and select among available items offered by entities185. Furthermore, users 197 can request a service related to the user'sselection. The network system 100 can identify one or more serviceproviders 192 and transmit invitations to the provider devices 190 toinvite the service providers 192 to provide the requested service to aservice location. In addition, the network system 100 communicates withentities 185 to transmit data related to the user's 197 request to theentities 185 and receive data regarding status information. As usedherein, the user device 195 and the provider device 190 can comprisemobile computing devices (e.g., smartphones, tablet computers, smartwatches, etc.), VR or AR headsets, desktop computers, on-board computingsystems of vehicles, and the like. In addition, the service provider 192and provider device 190 can be on-board computing systems of autonomousvehicles.

According to embodiments, the network system 100 can include a userdevice interface 140 to communicate with user devices 195 over one ormore networks 180 via a user application 196. According to examples, arequesting user 197 wishing to utilize the network service can launch orinteract with user application 196 on the requesting user's user device195. The user application 196 can submit a query 198 to the networksystem 100 over network 180. The query 198 can include data regarding aservice location. The user application 196 can determine the servicelocation based on location data generated by the user device 195 (e.g.,GPS data) that indicates the user's current location. The user device195 can transmit query 198 automatically in response to the user'slaunching or activating of the user application 196 on the user device195. In some examples, the user application 196 can store a defaultservice location such that the query 198 transmitted in response to theuser's launching or activating the user application 196 includes dataregarding the default service location. The default service location canbe the user's 197 home location, work location, or last-used servicelocation. The query 198 can also be submitted in response to a userselection of or interaction with a user interface feature within theuser application 196. The user 197 can also provide a service locationby entering an address, searching for a nearby point of interest, orselecting a location on an interactive map within the user application196. In some examples, the query 198 can be transmitted without useractivation of or user interaction with the user application 196. Forinstance, the user application 196 can transmit the query periodicallyor automatically in response to detecting a change in the user'slocation while the user application 196 is being executed in thebackground on the user device 195. In addition, the query 198 can betransmitted by an operating system of the user device 195 or a componentthereof. In some cases, the query 198 can also represent datacorresponding to a desired service time.

According to embodiments, query processing 115 receives the query 198and, in response, determines available entities 116 and items 117. Theavailable entities 116 can be identified from the plurality of entities185 based on their geographic location as compared with the servicelocation indicated in the query 198. For example, the query processing115 can identify entities 116 located within a certain distance of theservice location, within a certain estimated time of travel from theservice location, etc. In addition, the query processing 115 canidentify available entities 116 based on their hours of operation ascompared with a time of receipt of the query 198 or a service timeindicated in the query 198. The available items 117 can correspond toitems provided or offered by the entities 116 that can be selected bythe user 197 in association with a service request.

According to embodiments, the user device interface 140 transmits dataregarding the available entities 116 and items 117 to the requestinguser device 195. The data can be transmitted as content data 141 fordisplay on the user device 195 within the user application 196. Forinstance, the user device interface 140 can include a user contentengine to generate the content data 141. The content data can cause theuser application 196 to display the available entities 116 and items 117for viewing and selection by the requesting user 197. In variousaspects, content data 141 corresponding to the available items 116includes information regarding the entities 116 and items 117 including,for example, reviews regarding the entities 116 and items 117, pricesassociated with the items 117, estimated preparation times associatedwith the items 117, and the like. In this manner, the requesting user197 can view value information associated with each of the availableitems 117 in making his or her selection among the available items 117.

In various aspects, the network system 100 further includes a parameterengine 110 to determine a set of parameters 111 in response to the query198. The set of parameters 111 can indicate booking fees, delivery fees,or service fees to be charged to the requesting user 197 in associationwith requesting for the network service. Each of the set of parameters111 can be associated with an available entity 116 identified by queryprocessing 115. In other words, each available entity 116 can beassociated with a different parameter. The set of parameters 111 can bedetermined by the parameter engine 110 based on pending requests 154 orbased on historical data 155. In addition, each of the set of parameters111 can have a default value (e.g., a default flat rate). The usercontent data 141 generated by the user device interface can furtherinclude data to cause the user device 195 to display the set ofparameters 111 determined in response to the query 198.

According to embodiments, the request processing 125 receives, from therequesting user device 195 via the user device interface 140, request199 corresponding to a request for service. The request 199 can includedata indicating the requesting user's selection of item(s) from theavailable items 117. In response to receiving the request 199, therequest processing 125 can generate processed requests 128 to theentity(ies) relevant to the request 199 to inform the entity(ies) of therequesting user's selection and to enable the entity(ies) to beingpreparing the selected item(s). The processed request 128 can includetiming information to indicate to the entity(ies) when to beginpreparing the selected items. For instance, the timing information canindicate to the entity(ies) to begin preparing the selected itemsimmediately or in fifteen minutes. In addition, the request processing125 can determine to group two or more service requests 199 such that asingle service provider can fulfill the group of service requests 199.For instance, the request processing 125 can determine, based on acorresponding query 198 in response to which parameter 111 wasdynamically determined, that a received service request 199 is to begrouped with another pending service request.

According to embodiments, the network system 100 can include a providerrouting and selection engine 120 for identifying a service provider froma plurality of service providers 192 to service the request 199. Theservice provider can be identified based on its current locationrelative to the entity(ies) selected in the request 199. For instance,the network system 100 can maintain communications with each of theservice provider devices 190 to monitor the current locations of theservice providers 192. In response to the request 199, the requestprocessing 125 can identify a service provider based on its currentlocation being within a particular distance or travel time from theentity(ies) associated with the request 199. In some cases, the requestprocessing 125 can identify a service provider based on its providerclass. For instance, if the entity(ies) and/or the service location arelocated in a dense urban region, the provider routing and selectionengine 120 can identify a service provider having a provider classcorresponding to service providers operating motorcycles or bicyclesrather than automobiles. In addition, the identification of serviceproviders can be based on request group 127 received from requestprocessing 125. The request group 127 can indicate a group of servicerequests to be serviced by a single service provider. The providerselection and routing engine 120 can utilize this information toidentify service providers to fulfill service requests 199.

Upon identifying a service provider to fulfill the request 199, theprovider routing and selection engine 120 can generate an invitation122. The invitation can be transmitted by the provider device interface145 to the provider's provider device 190 via the network(s) 180. Inresponse, the identified service provider can accept or decline theinvitation 122. If the service provider accepts the invitation 122(e.g., via a selection within the provider application 191), the networksystem 100 can transmit to the provider device 190, for example, a route121 determined by the provider routing and selection engine 120 tofacilitate the fulfillment of the request 199 by the provider device. Ifthe service provider declines the invitation 122, the provider routingand selection engine 120 can identify another suitable service provider.

In the examples described herein, the provider routing and selectionengine 120 can also determine a route 121. The route 121 can betransmitted to the selected service provider to follow in fulfilling therequested service. The route 121 can include a route segment(s) to theentity(ies) and a route segment(s) to the service location(s). Forexample, if the service provider is identified by the network system 100to fulfill service requests 199 requesting items from more than entity,the route 121 can include a first route segment from the currentlocation of the selected service provider to a first one of theentities, a second route segment from the first one of the entities to asecond one of the entities, etc. Furthermore, if the service provider isidentified by the network system 100 to fulfill service requests 199having different service locations, the route 121 can include a segmentfrom the last one of the entities to the first one of the servicelocations, a segment from the first one of the service locations to asecond one of the service locations, etc.

In some implementations, the provider routing and selection engine 120can optimize the route 121 based on preparation times associated withthe one or more selected items of the request 199. For example, theprovider routing and selection engine 120 can optimize the route 121 tominimize wait times for the service provider as well as the requestinguser. For example, based on the preparation times, the provider routingand selection engine 120 can determine the optimal route such that theservice provider arrives at the location of an entity at or around thetime that a selected item being prepared by the entity is estimated tobe ready for pick-up. The provider routing and selection engine 120 canfurther optimize the route 121 by determining an order of entities onthe route based on the preparation times of the one or more selecteditems. The network system can additionally optimize the route to reducetravel distance and/or time. In this manner, wait times for both theservice provider 192 and the requesting user 197 can be minimized.

According to embodiments, the provider routing and selection engine 120can dynamically update the route based on real-time data from theentities 185 regarding status of the one or more selected items (e.g.,preparation status, etc.). Accordingly, the route for the selectedservice provider can be dynamically updated to take into account, forexample, any delays at the entities 185 in preparing the one or moreselected items. Furthermore, the provider routing and selection engine120 can further optimize the route to minimize the travel distanceand/or travel time. For example, the provider routing and selectionengine 120 can take into account traffic information to optimize theroute to reduce travel distance and/or travel time. The provider routingand selection engine 120 can also be configured to dynamically balancethe various factors and parameters being optimized (e.g., traveldistance, travel time, service provider wait time, requesting user waittime, item idle time (e.g., time after item is prepared and before beingpicked up by the selected service provider), etc.) in determining theoptimal route. For instance, during a time period of service providershortage, the provider routing and selection engine 120 can determinethe optimal route such that service provider wait time is weighted moreheavily in the optimization process.

According to embodiments, the database 150 of the network system 100 canstore information such as user profiles 156, entity profiles 157, andhistorical data 158. A user profile 156 can store information such as acorresponding user's preferences in items offered by entities (e.g.,item preference, favorite entities, favorite item genre, disliked items,food allergies, etc.). The user profile 156 can also store the user'smost frequently used or favorite service locations (e.g., work, home,etc.). In addition, the user profile 156 can store information regardingthe user's past service requests submitted to the network system 100(e.g., items requested, amount spent, etc.). Using information stored inthe user profiles 156, the network system 100 can optimize thecorresponding users' 197 experiences. For instance, the network system100 can generate item or entity suggestions or recommendations based oninformation stored in the user profiles 156.

The entity profiles 157 can store information such as an entity'sperformance record with respect to preparing items in accordance withthe items' associated preparation times. For instance, an entity profile157 may indicate that an entity, based on historical records, hasprepared items within their respective preparation times 95% of thetime. This information can be transmitted to user device 195 for viewingby a requesting user 197 while the user is viewing available items forselection. In addition, entity profiles 157 can store information suchas user reviews and/or ratings of the entities' performance and qualityof the items offered by the entities. The database 150 can storehistorical data 158 in the form of item profiles including informationrelated to each item offered by entities 185 in the given geographicregion managed by the network system 100. Such information includes, forexample, an associated preparation time, ingredient information, andhistorical value data, etc.

Methodology

FIG. 2 is a flow chart describing an example method of operating anexemplary network system, according to examples described herein. In thebelow discussion of FIG. 2, reference may be made to features andexamples shown and described with respect to FIG. 1. For instance, theprocess described with respect to FIG. 2 may be performed by an examplenetwork system such as the one shown and described with respect to FIG.1.

Referring to FIG. 2, a network system (e.g., network system 100 ofFIG. 1) can receive a query from a user device (e.g., user device 195 ofFIG. 1) operated by a user over a network (211). The query can betransmitted by the user device in response to user interactions with auser application executing on the user device (e.g., opening orlaunching the user application, selecting or activating a user interfacefeature, etc.). The query received from the user device can include aservice location 211-1 and/or a desired service time 211-2. The servicelocation 211-1 can be determined based on geo-location data generated bythe user device (e.g., GPS, GLONASS, or Galileo data etc.), entered bythe user through the user application (e.g., by entering an address, bysearching a name or location, by selecting on an interactive map, etc.),or auto-populated based on historical data pertaining to the user (e.g.,a home location, a work location, a favorite location, etc.). Thedesired service time 211-2 can correspond to a desired time at which therequested service is to be fulfilled (e.g., a time at which the serviceprovider is to rendezvous with the requesting user). By selecting adesired service time 211-2, the requesting user can schedule a serviceto be performed at a specific time. The network system can makedeterminations for various aspects of the requested service for therequesting user based on the service location 211-1 and the desiredservice time 211-2 (e.g., identifying available entities nearby inresponse to the query).

In the examples described herein, the network system can identifyavailable entities and/or available items offered by the availableentities (212). The network system can identify available entities basedon the service location 211-1. For instance, the network system canidentify entities that are within a certain distance from the servicelocation or within a certain estimated time of travel away from theservice location. The network system can also identify entities based onthe desired service time 211-2. For example, the network system canexclude entities that are outside their operating hours at or around thedesired service time.

According to embodiments, the network system can determine values for aset of parameters in response to the query (213). The values of the setof parameters can be default values or dynamically determined values.Each of the parameters can be associated with an available entity. Forinstance, in identifying four available entities that are nearby to theservice location, the network system can determine four parameters, eachparameter being associated with one of the available entities. Thenetwork system can determine the values of the set of parameters basedon pending service requests or based on anticipated demand. For example,the network system can determine that there is at least pending oneservice request for items from a particular entity to the servicelocation indicated in the received query. In response, the networksystem can dynamically compute the value of the parameter associatedwith the particular entity based on the determination. In addition, thenetwork system can determine a time interval for which the dynamicallycomputed parameter value is to be in effect. For instance, if thepending service request is estimated to be picked up by a serviceprovider from the particular entity within thirty minutes, the timeinterval can be determined to be a maximum of thirty minutes.

In the examples described herein, the network system can transmit dataregarding the available entities and their associated parameters to therequesting user device (214). Data transmitted to the requesting userdevice can include content data for displaying content regarding theavailable entities and the parameters on the user devices. For example,data transmitted by the network system can cause or enable the userdevices to display a list of available entities and their associatedparameter values. The requesting user can view and interact with thelists to select an entity in association with making a service request.In addition, the content data can include data corresponding to arecommendation or a promotion for display on the user device. Thedisplay of the recommendation or promotion can include the dynamicallycomputed parameter value and the associated time interval for which theparameter value is to be valid. In addition, the content data caninclude data to display items for selection at each of the availableentities (e.g., menu items). Furthermore, the content data can includerelevant information such as user reviews or ratings of available itemsand/or each of the plurality of entities, images of the available items,etc. Additionally, the content data can include one or more suggesteditems for the requesting user based on the requesting user'spreferences. For example, the content data can include an itemcomplements suggestion indicating a plurality of items that therequesting user may enjoy at the same time (e.g., a suggested item thatwould complement a selected item).

According to embodiments, the network system can receive a request fromthe user device (215). The request can include data regarding the user'sselection of one or more items for service to the service location211-1. The request can be generated by the user device in response tothe requesting user's interaction with the user application (e.g., usinga “Submit” or “Place Order” user interface feature).

In various examples, in response to receiving the request at step 215,the network system transmits request information to the relevantentity(ies) (216). In some examples, the request information includes adesired preparation completion time. The desired preparation completiontime can be a time for the entity to complete preparation of acorresponding item that is estimated by the network system to ensurethat the request is fulfilled in a timely manner (e.g., at or around thedesired service time 211-2). As an alternative, the network system cantransmit information to enable the entity(ies) to prepare items based onhistorical data relating to demand.

According to embodiments, the network system further determines anoptimal route for a service provider in fulfilling the request forservice (217). This step may be performed, for example, by serviceprovider routing and selection engine 120 of FIG. 1. In particular, theoptimal routes can be determined based on preparation times associatedwith the one or more selected items to, for example, minimize wait timesfor the selected service provider as well as the requesting user. Forexample, based on the preparation times, the network system candetermine the optimal route such that the selected service providerarrives at the location of an entity at or around the time that aselected item being prepared by the entity is estimated to be ready forpick-up. The network system can further optimize the route bydetermining a sequence of entities on the route based on the preparationtimes of the selected items. The network system can additionallyoptimize the route to reduce travel distance and/or time. In addition,the network system can receive real-time data from entities to updatethe optimal route. For example, based on real-time data indicatingdelays at one particular entity, the network system can update theoptimal route to account for the delays (e.g., re-order the order ofentities or delaying the route segment to the particular entityexperiencing the delays). In this manner, the route for the serviceprovider can remain optimal based on up-to-date information.

In various aspects, the network system can identify or select a serviceprovider from a plurality of service providers to fulfill the requestfor service (218). For instance, the network system can select a serviceprovider located proximately to an entity and/or the service location.Additionally, the network system can select a service provider based onthe optimal route. For instance, the network system can select a bicycleservice provider based on the optimal route being within a dense urbanenvironment. In contrast, if the optimal route includes one or moresegments over a freeway or highway, the network system can select anautomobile service provider. In addition, the network system canidentify a service provider based on a service capacity associatedtherewith. For instance, the network system can determine a requiredservice capacity based on items selected by requesting users in a groupof service requests to be serviced by a single service provider. Thenetwork system can identify a service provider such that the servicecapacity of the service provider is sufficient in fulfilling the groupof service requests.

According to embodiments, the network system can transmit datacorresponding to the optimal route to the selected service provider(219). The data corresponding to the optimal route can include contentdata, such as map data to enable or cause a provider device of theselected provider to display route guidance or an interactive map thatincludes the optimal route.

User Interface Descriptions

FIGS. 3A-3D are figures illustrating exemplary user interfaces for auser application for a network service, as described herein. Referringto FIG. 3A, a user interface for a user application is illustrated. Theuser interface illustrated in FIG. 3A can be displayed after a query istransmitted (e.g., when the user app initializes) to a network systemmanaging the network service. The user interface displays informationregarding multiple entities (e.g., Restaurant C, Restaurant D). Inaddition, the user interface displays information regarding theparameters associated with the entities. For the first entity displayedwithin the user interface (Restaurant C), parameter information 310 isdisplayed. Parameter information 310 indicates that a default parameter($3) will be applied to a service request submitted by the user for thefirst entity via the user application. For the second entity displayedwithin the user interface (Restaurant D), parameter information 320 isdisplayed. Parameter information 320 indicates that a dynamicallydetermined parameter ($1) will be applied to a service request submittedby the user for the second entity via the user application. In addition,user application displays an indicator 321, a downward arrow, toindicate that the parameter value is dynamically determined and lowerthan the default value.

User interface illustrated in FIG. 3B shows a promotion 330 generated inresponse to a query submitted by the user device. The promotion 330indicates that the parameter associated with an entity (Restaurant A) isdynamically determined to be lower than the default value ($3 lower).Referring to FIG. 3C, another user interface displaying a promotion 330is illustrated. This user interface displays information specific to anentity (Restaurant A). The promotion 330 relays to the user that thedynamically determined parameter is lower than the default value. Inaddition, the parameter 330 further indicates a time interval for whichthe dynamically determined parameter is to be valid (30 minutes).

Referring to FIG. 3D, a home screen or lock screen of a user device isillustrated. A push notification 340 is displayed on the screen of theuser device. The push notification 340 indicates that a particularentity (Restaurant A) currently has a dynamically determined parameterthat is lower than the default value. The user can interact with thepush notification to open the user application to submit a servicerequest.

Hardware Diagram

FIG. 4 is a block diagram that illustrates a computer system upon whichexamples described herein may be implemented. A computer system 400 canbe implemented on, for example, a server or combination of servers. Forexample, the computer system 400 may be implemented as part of a networkservice, such as described in FIGS. 1 through 6. In the context of FIG.1, the network system 100 may be implemented using a computer system 400such as described by FIG. 4. The network system 100 and may also beimplemented using a combination of multiple computer systems asdescribed in connection with FIG. 4.

In one implementation, the computer system 400 includes processingresources 410, a main memory 420, a read-only memory (ROM) 430, astorage device 440, and a communication interface 450. The computersystem 400 includes at least one processor 410 for processinginformation stored in the main memory 420, such as provided by a randomaccess memory (RAM) or other dynamic storage device, for storinginformation and instructions which are executable by the processor 410.The main memory 420 also may be used for storing temporary variables orother intermediate information during execution of instructions to beexecuted by the processor 410. The computer system 400 may also includethe ROM 430 or other static storage device for storing staticinformation and instructions for the processor 410. A storage device440, such as a magnetic disk or optical disk, is provided for storinginformation and instructions.

The communication interface 450 enables the computer system 400 tocommunicate with one or more networks 480 (e.g., cellular network)through use of the network link (wireless or wired). Using the networklink, the computer system 400 can communicate with one or more computingdevices, one or more servers, one or more databases, and/or one or moreself-driving vehicles. In accordance with examples, the computer system400 receives requests 482 from mobile computing devices of individualusers. The executable instructions stored in the memory 430 can includeprovider routing and selection instructions 422, which the processor 410executes to determine an optimal route and select a service provider toservice the request 482.

The executable instructions stored in the memory 420 can also includecontent generation instructions 424, which enable the computer system400 to access user profiles 426 and other user information in order toselect and/or generate user content 454 for display on the user devices.As described throughout, user content 454 can be generated based oninformation pertaining to the state of the request (e.g., statusinformation). By way of example, the instructions and data stored in thememory 420 can be executed by the processor 410 to implement an examplenetwork system 100 of FIG. 1. In performing the operations, theprocessor 410 can receive requests 482 and service provider locations484, and submit invitation messages 452 to facilitate the servicing ofthe requests 482. The processor 410 is configured with software and/orother logic to perform one or more processes, steps and other functionsdescribed with implementations, such as described by FIGS. 1 to 4, andelsewhere in the present application.

Examples described herein are related to the use of the computer system400 for implementing the techniques described herein. According to oneexample, those techniques are performed by the computer system 400 inresponse to the processor 410 executing one or more sequences of one ormore instructions contained in the main memory 420. Such instructionsmay be read into the main memory 420 from another machine-readablemedium, such as the storage device 440. Execution of the sequences ofinstructions contained in the main memory 420 causes the processor 410to perform the process steps described herein. In alternativeimplementations, hard-wired circuitry may be used in place of or incombination with software instructions to implement examples describedherein. Thus, the examples described are not limited to any specificcombination of hardware circuitry and software.

User Device

FIG. 5 is a block diagram illustrating an example user device executingand operating a designated user application for communicating with anetwork service, according to examples described herein. In manyimplementations, the user device 500 can comprise a mobile computingdevice, such as a smartphone, tablet computer, laptop computer, VR or ARheadset device, and the like. As such, the user device 500 can includetypical telephony features such as a microphone 545, a camera 550, and acommunication interface 510 to communicate with external entities usingany number of wireless communication protocols. In certain aspects, theuser device 500 can store a designated application (e.g., a user app532) in a local memory 530. In variations, the memory 530 can storeadditional applications executable by one or more processors 540 of theuser device 500, enabling access and interaction with one or more hostservers over one or more networks 580.

In response to a user input 518, the user app 532 can be executed by aprocessor 540, which can cause an app interface 542 to be generated on adisplay screen 520 of the user device 500. The app interface 542 canenable the user to, for example, view available items offered by nearbyentities. In various implementations, the app interface 542 can furtherenable the user to enter or select a service location (e.g., by enteringan address, performing a search, or selecting on an interactive map).Furthermore, the app interface 542 can display dynamically determinedvalues associated with the available items. The user can generate arequest 567 via user inputs 518 provided on the app interface 542. Forexample, the user can select one or more items from the available itemsin requesting the network service. In some examples, the app interface542 can display one or more suggested or recommended items that areidentified by the network system based on information specific to theuser (e.g., user profile information).

As provided herein, the user application 532 can further enable acommunication link with a network system 590 over the network 580, suchas the network system 100 as shown and described with respect to FIG. 1.The processor 540 can generate user interface features 528 (e.g., map,request status, content cards, etc.) using content data 526 receivedfrom the network system 590 over network 580. Furthermore, as discussedherein, the user application 532 can enable the network system 590 tocause the generated user interface 528 to be displayed on theapplication interface 542.

The processor 540 can transmit the requests 567 via a communicationsinterface 510 to the backend network system 590 over a network 580. Inresponse, the user device 500 can receive a confirmation 569 from thenetwork system 590 indicating the selected service provider that willservice the request 567. In various examples, the user device 500 canfurther include a GPS module 560, which can provide location data 562indicating the current location of the requesting user to the networksystem 590 to, for example, establish the service location.

According to embodiments, the app interface 542 can further display userinterface features indicating or representing a current status of therequest for service. For instance, the app interface 542 can display aprogress bar indicating the current status of the user's request. Theapp interface 542 can also display useful information such as anestimated time of arrival of the selected service provider at theservice location. In addition, the user can enter, via the app interface542, information that may be relevant to the selected service providersuch as a building entry access code, an intercom number or code, acontact phone number of the user, a cross-street etc.

Service Provider Device

FIG. 6 is a block diagram illustrating an example service providerdevice executing and operating a designated service provider applicationfor communicating with a network service, according to examplesdescribed herein. In many implementations, the service provider device600 can comprise a mobile computing device, such as a smartphone, tabletcomputer, laptop computer, VR or AR headset device, and the like. Assuch, the service provider device 600 can include typical telephonyfeatures such as a microphone 645, a camera 650, and a communicationinterface 610 to communicate with external entities using any number ofwireless communication protocols. The service provider device 600 canstore a designated application (e.g., a service provider app 632) in alocal memory 630. In response to a service provider input 618, theservice provider app 632 can be executed by a processor 640, which cancause an app interface 642 to be generated on a display screen 620 ofthe service provider device 600. The app interface 642 can enable theservice provider to, for example, accept or reject invitations 692 inorder to service requests throughout a given region.

In various examples, the service provider device 600 can include a GPSmodule 660, which can provide location data 662 indicating the currentlocation of the service provider to the network system 690 over anetwork 680. Thus, the network system 690 can utilize the currentlocation 662 of the service provider to determine whether the serviceprovider is optimally located to service a particular request. If theservice provider is optimal to service the request, the network system690 can transmit an invitation 692 to the service provider device 600over the network 680. The invitation 692 can be displayed on the appinterface 642, and can be accepted or declined by the service provider.If the service provider accepts the invitation 692, then the serviceprovider can provide a service provider input 618 on the displayed appinterface 642 to provide a confirmation 622 to the network system 690indicating that the service provider will follow a route 693 receivedfrom the network system 690 to fulfill the requested service.

It is contemplated for examples described herein to extend to individualelements and concepts described herein, independently of other concepts,ideas or systems, as well as for examples to include combinations ofelements recited anywhere in this application. Although examples aredescribed in detail herein with reference to the accompanying drawings,it is to be understood that the concepts are not limited to thoseprecise examples. As such, many modifications and variations will beapparent to practitioners skilled in this art. Accordingly, it isintended that the scope of the concepts be defined by the followingclaims and their equivalents. Furthermore, it is contemplated that aparticular feature described either individually or as part of anexample can be combined with other individually described features, orparts of other examples, even if the other features and examples make nomentioned of the particular feature. Thus, the absence of describingcombinations should not preclude claiming rights to such combinations.

What is claimed is:
 1. A network system, for providing a network serviceover a given geographic region, comprising: one or more processors; andone or more memory resources storing instructions that, when executed bythe one or more processors, cause the network system to: receive, from afirst user device of a first user, a first set of data corresponding toa first service request associated with a selected entity, the first setof data indicating a first service location and a first service timeassociated with the first service request; receive, from a second userdevice of a second user, a second set of data corresponding to a query,the second set of data indicating a second service location and a secondservice time associated with the query; determine whether the secondservice location is located within a distance of the first servicelocation and whether the second service time is within a duration oftime of the first service time; compute, based on the determination, aparameter associated with the selected entity.
 2. The network system ofclaim 1, wherein computing the parameter associated with the selectedentity comprises: (i) determining a predetermined value for theparameter based on a determination that the second service location isnot located within the distance of the first service location or thatthe second service time is not within the duration of time of the firstservice time; and (ii) computing a value for the parameter based on thedetermination that the second service location is located within thedistance of the first service location and that the second service timeis within the duration of time of the first service time.
 3. The networksystem of claim 1, wherein the parameter is computed based on a numberof service requests associated with the selected entity, each of theservice requests having a respective service location located within thedistance of the first service location and a respective service timewithin the duration of time of the first service time.
 4. The networksystem of claim 1, wherein the executed instructions further cause thenetwork system to: receive, from the second user device, a third set ofdata corresponding to a second service request associated with theselected entity, the third set of data indicating the second servicelocation and the second service time; based on the determination thatthe second service location is located within the distance of the firstservice location and that the second service time is within the durationof time of the first service time: select a first service provider froma group of service providers to be assigned to the first service requestand the second service request; and transmit, to a provider device ofthe first service provider, a fourth set of data, including datacorresponding to a route.
 5. The network system of claim 7, wherein theroute includes a route segment to the selected entity, a route segmentto the first service location, and a route segment to the second servicelocation.
 6. The network system of claim 7, wherein the computedparameter is associated with second service request.
 7. The networksystem of claim 1, wherein the executed instructions further cause thenetwork system to: receive, from the second user device, a third set ofdata corresponding to a second service request associated with theselected entity, the third set of data indicating the second servicelocation and the second service time; based on the determination thatthe second service location is not located within the distance of thefirst service location or that the second service time is not within theduration of time of the first service time: select a first serviceprovider from a group of service providers to be assigned to the firstservice request and a second service provider from the group of serviceproviders to be assigned to the second service request; transmit, to afirst provider device of the first service provider, a fourth set ofdata, including data corresponding to a first route, the first routehaving a route segment to the selected entity and a route segment to thefirst service location; and transmit to a second provider device of thesecond service provider, a fifth set of data, including datacorresponding to a second route, the second route having a route segmentto the selected entity and a route segment to the second servicelocation.
 8. The network system of claim 1, wherein the executedinstructions further cause the network system to transmit content datato the second user device to enable the second user device to display arecommendation relating to the selected entity, the recommendationincluding information pertaining to the computed parameter.
 9. Acomputer-implemented method for providing a service over a givengeographic region, the method being performed by one or more processorsand comprising: receiving, from a first user device of a first user, afirst set of data corresponding to a first service request associatedwith a selected entity, the first set of data indicating a first servicelocation and a first service time associated with the first servicerequest; receiving, from a second user device of a second user, a secondset of data corresponding to a query, the second set of data indicatinga second service location and a second service time associated with thequery; determining whether the second service location is located withina distance of the first service location and whether the second servicetime is within a duration of time of the first service time; computing,based on the determination, a parameter associated with the selectedentity.
 10. The computer-implemented method of claim 10, whereincomputing the parameter associated with the selected entity comprises:(i) determining a predetermined value for the parameter based on adetermination that the second service location is not located within thedistance of the first service location or that the second service timeis not within the duration of time of the first service time; and (ii)computing a value for the parameter based on the determination that thesecond service location is located within the distance of the firstservice location and that the second service time is within the durationof time of the first service time.
 11. The computer-implemented methodof claim 10, wherein the parameter is computed is based on a number ofservice requests associated with the selected entity, each of theservice requests having a respective service location located within thedistance of the first service location and a respective service timewithin the duration of time of the first service time.
 12. Thecomputer-implemented method of claim 10, further comprising transmittingcontent data to the second user device to enable the second user deviceto display a recommendation relating to the selected entity, therecommendation including information pertaining to the computedparameter.
 13. A network system for providing a network service over agiven geographic region, comprising: one or more processors; and one ormore memory resources storing instructions that, when executed by theone or more processors, cause the network system to: receive, from auser device of a user, query data corresponding to a query, the querydata indicating a service location and a service time associated withthe query; in response to the query, determine, based on historical dataassociated with the network service, a plurality of metrics, each of theplurality of metrics being associated with the service location, theservice time, and a corresponding one of a plurality of entities; anddetermine, based on the plurality of metrics, a plurality of parameters,each of the plurality parameters being associated with a correspondingone of the plurality of entities.
 14. The network system of claim 15,wherein each of the plurality of metrics is indicative of a level ofexpected demand for the network service associated with a correspondingone of the plurality of entities.
 15. The network system of claim 15,wherein determining the plurality of parameters comprises assigning oneof the plurality of parameters a default value in the event that acorresponding one of the plurality metrics is below a threshold value.16. The network system of claim 15, wherein determining the plurality ofparameters comprises dynamically computing one of the plurality ofparameters in the event that a corresponding one of the pluralitymetrics exceeds a threshold value.
 17. The network system of claim 15,wherein the executed instructions further cause the network system toreceive, from the user device, request data corresponding to a servicerequest for items associated with one of the plurality of entities. 18.The network system of claim 19, wherein the executed instructionsfurther cause the network system to associate a corresponding one of theplurality of parameters with the service request.
 19. The network systemof claim 10, wherein the executed instructions further cause the networksystem to transmit content data to the user device to enable the userdevice to display a recommendation relating to the selected entity, therecommendation including information pertaining to the computedparameter.
 20. The network system of claim 10, wherein the executedinstructions further cause the network system to transmit data to one ormore other user devices to enable the one or more other user devices toeach display a notification regarding at least one of the plurality ofparameters.